I've read with interest some of the recent discussions regarding
setting up a database to track letterbox status, etc.
First, although I'm one of the 'old timers', for various reasons, I've
not been doing the 'heavy lifting'' that has kept the site and the
hobby growing, so kudos to the many that do, and I agree that they all
have enough to do just keeping up. If it ain't broke,,....etc. So this
is NOT intended to induce any 'boat-rocking'.

So this post is for the database-folks who are looking for ways to
channel their enthusiasm for the hobby in helpful directions. Others
lacking this interest might choose to skip the rest of this
post.........

The database discussion echoes a similar vein of about a year and a
half ago, both on-line and at a small gathering in southern VT. At
that, translating clues into a database format seemed unnecessary
cumbersome for that time and scale of things, and likely to encumber
what was then a pretty smooth process of clue-posting by an ad-hoc
regional division of responsibility. At that time, I didn't even have
a database program. But we pretty much agreed that any large explosion
of letterbox population might become a burden to those that have taken
on the work under the system then in place.

At that time, I was envisioning linking a database with GIS software
(specifically, ESRI's "Arc-View"-which I have, and licensed for use
with my local planning commission, but with which am not particularly
facile). While there are other programs out there, ESRI's software is
the software of choice for most geographic-base planning as far as I
know. They have a web-site for those interested. http://www.esri.com/

This software, if purchased for legal LBNA licensed use, is about
$1,000. What it would offer is easy conversion from database info into
a variety of geographic-based graphic formats, say for example, a red
dot on a world or US or state or county map(s) hyperlinked to the
database page(s) or clue page for each letterbox. It was pretty much
agreed then that as nice as this in theory, getting it up and running
would be onerous, fraught with unknowns, and expensive to get a legal
software license that could be shared among the LBNA Webmasters. With
which I agreed then, and probably still do now.

However, and the point of this lengthy post, is to suggest (1) that
any database work done for LBNA be translatable (now or in the future)
to the Arc-View platform, which translates now to using (or something
convertible into) Microsoft Access as a (Windows) database platform.
ArcView has its own internal database software, but can easily import
Access although it may accept others as well. And, (2) it needs a
geographic locator in one (or more) fields, for each letterbox in
order to generate a map. It will read (within the US) all
municipalities, all counties, all US zip-code districts,
latitude/longitude points, plus lots of other map objects. It can read
and plot terrain models (topo at the scale appropriate to the map,
road networks, and all kinds of things that go beyond our likely
needs. It will accept (I believe) 'either/or' searches, so having the
same locator field for ALL clues is not necessary, as long as at least
one exists. It places a marker (or several evenly distributed) equally
within the locator field (say, a municipality), or, directly on the
letterbox site in the case of lat/longitude or other more specific
info availability.

I AM NOT at all suggested publishing letterbox clues to the degree of
specificity available with GPS hardware - save that for the
geo-caching folks. I am saying that (1) most clues now have something
to give a general-enough location for the database, and (2) several
locator options are available to give new clue-writers several options
that will work.

My point to all this is to keep the long view in mind if someone
undertakes building a database, whether or not it becomes part of the
clue-submittal process now. Please consider setting it up for future
GIS-compatibility early-on.

At some point, clue-submittals could be sent in via a template form,
which in turn integrates automatically into the database. The
webmaster(s) running the software then repost the appropriate map(s),
which are automatically updated with new info. This might then easily
be scheduled at some more predictable interval (each month? Each two
weeks?). File size and where it will be hosted will always present a
problem, as I am sure it does now.

This is all very utopian I know, and my apologies to my fellow
webmasters who toil quietly and are saying (gad - not Erik and this
old saw yet again). LBNA is a great thing, obviously bringing lots of
happiness to lots of families, which has always been the main point.
Long may you run!

Erik (The Vermont Viking) in beautiful Vermont